v1.12.0 Release Notes

Zadig v1.12.0 was released on June 1, 2022.

# Feature List

Developer Tools

• Support VS Code Plugin

Project

• Support code scanning
• Support service association with multiple builds
• K8s YAML projects support importing services from existing K8s
• Support synchronizing service configurations from Gitee code repositories
• Support automatic environment updates after service configuration changes
• Support independent management of host login permissions
• K8s YAML project variable editor supports multi-line input

Template Library

• Support global build templates
• Support importing Helm Chart templates from Gitee code source
• Support automatic service configuration updates after K8s YAML template/Helm Chart template changes

Environment

• K8s Helm Chart environments support self-test mode
• K8s Helm Chart environments support Release view

Workflow

• Support configuring multiple IM notifications
• Support custom build code filtering rules

System Settings

• Support configuring global system permissions
• Support integrating multiple Jenkins
• Support configuring default login page
• Host management supports HTTP/HTTPS health checks
• Support integrating code sources with standard Git protocol
• Support pulling code from non-owner repositories
• Multi-cluster management upgrade capability enhanced
• Support dind multi-replica

Optimizations and Fixes

• Frontend button-level permission control
• Service list in environment supports one-click refresh
• Fixed issue where K8s YAML projects using version rollback versions cannot create environments
• Fixed issue where image cleanup function cannot continue cleaning when status is abnormal

# Version Upgrade Process

# Database Backup

If already in production use, be sure to backup the database before upgrading

1. Database backup commands:

• Backup MongoDB data

mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH

• Backup MySQL data

mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql

2. Database restore commands:

• Restore MongoDB data

mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH

• Restore MySQL data

# Execute the following in MySQL:
mysql> drop database user;
mysql> create database user;
mysql> drop database dex;
mysql> create database dex;
# Execute the following data recovery operations from command line:
mysql -h <HOST> -P <PORT> -u root -p user < user.sql
mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql

# Upgrade Operations

Please execute corresponding upgrade steps according to different installation methods.

# Installation Method: All in One Installation Mode or Installation on Existing Kubernetes

For both installation methods, use scripts from Installation on Existing Kubernetes^New for upgrade.

# Installation Method: Helm Command Installation

For this installation method, execute the following steps to upgrade to v1.12.0:

1. Execute the following command and check the zadig.yaml file. If the file contains image information (i.e., tag:a.b.c), it needs to be manually deleted.

helm get values <Release Name> -n <Zadig Namespace>  > zadig.yaml

2. Execute upgrade command according to installation method.

• Domain method:

export NAMESPACE=<Zadig Installation NAMESPACE>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.12.0

• IP + PORT method:

export NAMESPACE=<Zadig Installation NAMESPACE>
export PORT=<Any port between 30000-32767, different from initially used port>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
    --set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} \
    --set gloo.gatewayProxies.gatewayProxy.service.type=NodePort --version=1.12.0